Skip to content

docs(changelog): runner egress policy foundation entry#83

Merged
indykish merged 2 commits into
mainfrom
chore/m84-egress-foundation-changelog
Jun 10, 2026
Merged

docs(changelog): runner egress policy foundation entry#83
indykish merged 2 commits into
mainfrom
chore/m84-egress-foundation-changelog

Conversation

@indykish

@indykish indykish commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Adds an Internal-tagged Jun 11, 2026 changelog entry for the merged egress-policy foundation (agentsfleet/agentsfleet#391): RUNNER_NETWORK_POLICY now selects the runner network posture — allow_all (default, behavior unchanged), deny_all_egress, and allow_list_egress (fails closed with UZ-RUN-007 until kernel enforcement ships in an upcoming release).

No user-visible behavior change; entry explicitly states the default stays today's posture. Landed now per Indy's direction instead of folding into the next user-visible release.

🤖 Generated with Claude Code

Greptile Summary

This PR adds a single changelog entry documenting the RUNNER_NETWORK_POLICY environment variable foundation (agentsfleet/agentsfleet#391), tagged Internal + Security. No user-visible behavior change is introduced — the entry explicitly states the default posture is unchanged.

  • New RUNNER_NETWORK_POLICY env var — documents the three values (allow_all, deny_all_egress, allow_list_egress) and their behavior; allow_list_egress is noted as failing closed with UZ-RUN-007 until kernel-level enforcement ships.
  • Forward-dated entry (Jun 11) — merged one day ahead of its label date per explicit direction; the prior Jun 10 entry below it preserves correct chronological order.

Confidence Score: 5/5

Documentation-only change; no code execution paths are affected.

The change is a single changelog entry documenting a new env var. The prose is accurate to the PR description, the MDX structure is valid, the Internal+Security tags are appropriate, and the prior comment about the nftables implementation-detail parenthetical has been resolved in this revision.

No files require special attention.

Important Files Changed

Filename Overview
changelog.mdx Adds an Internal+Security-tagged Jun 11, 2026 changelog entry documenting the RUNNER_NETWORK_POLICY env var and its three values; content is accurate and well-structured with no blocking issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Runner starts] --> B{RUNNER_NETWORK_POLICY\nenv var set?}
    B -- "unset / allow_all" --> C[Full outbound access\ncurrent default behavior]
    B -- "deny_all_egress" --> D[No outbound network]
    B -- "allow_list_egress" --> E{Kernel enforcement\nshipped?}
    E -- "No (current state)" --> F["Fails closed\nUZ-RUN-007"]
    E -- "Yes (upcoming release)" --> G[Outbound only to\npermitted destinations]
Loading

Reviews (2): Last reviewed commit: "docs(changelog): drop kernel-mechanism p..." | Re-trigger Greptile

Internal-tagged Jun 11 update: RUNNER_NETWORK_POLICY selects the runner
network posture (allow_all default — unchanged behavior, deny_all_egress,
allow_list_egress fail-closed UZ-RUN-007 until enforcement ships).
No user-visible behavior change; entry lands per Indy's ask rather than
folding into the next user-visible release.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Comment thread changelog.mdx Outdated
…y (greptile P2)

Operator docs stay at the operational level per AGENTS.md; the nftables/
netns mechanism belongs in main-repo playbooks, not the changelog.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Jun 10, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
megam 🟢 Ready View Preview Jun 10, 2026, 9:10 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@indykish indykish merged commit f17e103 into main Jun 10, 2026
4 checks passed
@indykish indykish deleted the chore/m84-egress-foundation-changelog branch June 10, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant